Method and system for interactive home monitoring

ABSTRACT

A method and system for interactive home monitoring includes detecting a visitor arriving at a premises of a multimedia content distribution network (MCDN) client by an intercom unit installed at the premises. The intercom unit may be coupled to the MCDN client, which may be configured to wirelessly communicate with a user of the MCDN client. A captured image of the visitor may be used to determine if an identity of the visitor is known or unknown. Based on the identity, a communication channel between the visitor and the user may be established at the intercom unit. The intercom unit may further be configured to provide further information to the visitor based on the visitor identity.

FIELD OF THE DISCLOSURE

The present disclosure relates to home monitoring and, moreparticularly, to interactive home monitoring using wireless telemetry.

BACKGROUND

Typical home security systems may provide monitoring and controlservices via a residential gateway and may depend upon a fixed networkconnection to operate. Typical fixed network connections are susceptibleto signal loss and/or disruption.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of selected elements of an embodiment ofmultimedia content distribution network (MCDN);

FIG. 2 is a block diagram of selected elements of an embodiment of anMCDN showing additional detail for the MCDN clients;

FIG. 3 is a block diagram of selected elements of an embodiment of amultimedia handling device (MHD);

FIG. 4 is a block diagram of selected elements of an embodiment of ahome monitoring system;

FIG. 5 illustrates selected elements of an embodiment of an interactivehome monitoring method;

FIG. 6 illustrates selected elements of an embodiment of an interactivehome monitoring method; and

FIG. 7 is a block diagram of selected elements of an embodiment of anintercom unit.

DESCRIPTION OF THE EMBODIMENT(S)

In one aspect, a disclosed method for providing interactive monitoringat a client premises of a multimedia content distribution network (MCDN)includes receiving, from an intercom unit, an arrival indicationindicating a visitor in proximity to the intercom unit and determiningan identity of the visitor based on a captured image of the visitor. Theintercom unit is coupled via an intercom link to a multimedia handlingdevice (MHD) at the client premises. The MHD may be or include a set topbox (STB). The method may further include establishing, with a wirelessinterface of the MHD, a wireless bidirectional audio communicationchannel between the MHD and a mobile user device associated with an MCDNuser of the client premises. The wireless bidirectional audiocommunication channel may be established based on the identity of thevisitor. The method may also include extending the communication channelvia the intercom link from the MHD to the intercom unit. Thecommunication channel may extend to a mobile user device at a locationthat is remote from the client premises. The mobile user device may be acellular telephone, a smart phone, a portable computer, a personalcomputer, or the like.

In certain embodiments, the communication channel between the MHD andthe mobile user device may be established as a push-to-talk connection,while the method may further include recording an audio message from thevisitor, and associating the recorded audio message with the identity ofthe visitor. Determining the identity may further include matching atleast a portion of the captured image with a previously stored image.The matching may be a result of a biometric analysis of a facial imageof the visitor. When the identity of the visitor is determined to be anew identity, the method may further include storing at least a portionof the captured image of the visitor. The method may further includereceiving a request from the MCDN user for a visitor report for aspecified period of time, sending the visitor report to the MCDN user,and providing the MCDN user access to stored images of the visitors. Thevisitor report may include arrival indications for visitors over thespecified period of time.

In a further aspect, a disclosed MHD for interactively monitoring aclient premises includes a processor coupled to memory media and awireless telemetry interface accessible to the processor. The memorymedia may include processor instructions executable to detect a visitorin proximity of the client premises and determine an identity of thevisitor based on an image received from an intercom unit incommunication with the MHD via an intercom link, and receive, via theintercom unit, an arrival indication initiated by the visitor. Theprocessor instructions may also be executable to enable an MCDN user tocommunicate with the visitor via the wireless telemetry interface. TheMHD may further be configured to use the wireless telemetry interface asa backup network interface when the MCDN is unavailable. The wirelesstelemetry interface may include a cellular telephony interface. Thecellular telephony interface may be provided by a cellular telephonedevice coupled to the processor. The intercom link may include at leastone of: a wireless link, an optical link, and a galvanic link.

In particular embodiments, the MHD may further include a networkconnection to a home security monitor, while the memory media mayfurther include processor instructions executable to receive, from thehome security monitor, sensor status information for at least onesecurity sensor installed at the client premises, and forward the sensorstatus information to the MCDN user. The memory media may furtherinclude processor instructions executable to receive control informationfrom the MCDN user to control an actuator installed at the clientpremises, and forward the control information to the home securitymonitor. The memory media may still further include processorinstructions executable to receive, from the home security monitor,activator status information indicating a state of the actuator, andforward the activator status information to the MCDN user.

In yet another aspect, a disclosed computer-readable memory mediaincludes executable instructions for monitoring the premises associatedwith an MCDN client. The instructions may be executable to detect avisitor arriving at the client premises based on an image and/or audiodate acquired by an intercom unit installed at the client premises.Based on a collection of stored visitor profiles and the acquired imageand/or audio data, a determination of whether the visitor is known orunknown may be made. Based on the visitor determination, theinstructions may be executable to output a visitor prompt using theintercom unit, while, when the visitor is known, the visitor prompt maybe specific to a known visitor identity. When the visitor is detectedand based on the visitor status, the instructions may be executable toestablish a communication channel between the intercom unit and anetwork address associated with a user MCDN associated with the client.

In some embodiments, the memory media may further include instructionsexecutable to receive, at the intercom unit, a request from the visitorfor premises information, and responsive to the request, output, via theintercom unit, premises information to the visitor based on the visitorstatus. The intercom unit may be configured to output multimediacontent, including at least one of: audio content, video content,images, and text. When the visitor is unknown, the instructions may beexecutable to add a new visitor profile, including the acquired imageand/or audio data, for the visitor in the collection. The networkaddress may include a cellular telephone number, while the communicationchannel may include a wireless telemetry channel. The network addressmay include an Internet-protocol address, while the communicationchannel may be established at least in part via the Internet. The memorymedia may further include instructions executable to use thecommunication channel to: notify the MCDN user that the visitor wasdetected, send the image and/or audio data to the MCDN user, send thevisitor status to the MCDN user, communicate bidirectionally between thevisitor and the MCDN user, communicate via audio, communicate via video,communicate via text, and/or receive instructions from the MCDN user forinterfacing with the visitor.

In the following description, details are set forth by way of example tofacilitate discussion of the disclosed subject matter. It should beapparent to a person of ordinary skill in the field, however, that thedisclosed embodiments are exemplary and not exhaustive of all possibleembodiments.

Throughout this disclosure, a hyphenated form of a reference numeralrefers to a specific instance of an element and the un-hyphenated formof the reference numeral refers to the element generically orcollectively. Thus, for example, widget 12-1 refers to an instance of awidget class, which may be referred to collectively as widgets 12 andany one of which may be referred to generically as a widget 12.

Turning now to the drawings, FIG. 1 is a block diagram illustratingselected elements of an embodiment of an MCDN 100. Although multimediacontent is not limited to TV, video on demand (VOD), or pay-per-view(PPV) programs, the depicted embodiments of MCDN 100 and itscapabilities are primarily described herein with reference to thesetypes of multimedia content, which are interchangeably referred toherein as “multimedia content”, “multimedia content programs”,“multimedia programs” or, simply, “programs.”

The elements of MCDN 100 illustrated in FIG. 1 depict networkembodiments with functionality for delivering multimedia content to aset of one or more subscribers. It is noted that different embodimentsof MCDN 100 may include additional elements or systems (not shown inFIG. 1 for clarity) as desired for additional functionality, such asdata processing systems for billing, content management, customersupport, operational support, or other business applications.

As depicted in FIG. 1, MCDN 100 includes one or more clients 120 and aservice provider 121. Each client 120 may represent a differentsubscriber of MCDN 100. In FIG. 1, a plurality of n clients 120 isdepicted as client 120-1, client 120-2 to client 120-n, where n may be alarge number. Clients 120 may include an intercom unit 322 (depicted inFIG. 3) and/or an MHD 125 for interactively monitoring client premisesas discussed below. Service provider 121 as depicted in FIG. 1encompasses resources to acquire, process, and deliver programs toclients 120 via access network 130. Such elements in FIG. 1 of serviceprovider 121 include content acquisition resources 180 connected toaggregation and switching network 140, referred to herein simply asswitching network 140, via backbone network 170, as well as applicationserver 150, database server 190, and content delivery server 160, alsoshown connected to switching network 140.

Access network 130 demarcates clients 120 and service provider 121, andprovides at least one connection path between clients 120 and serviceprovider 121. In some embodiments, access network 130 is an Internetprotocol (IP) compliant network. In some embodiments, access network 130is, at least in part, a coaxial cable network. It is noted that in someembodiments of MCDN 100, access network 130 is owned and/or operated byservice provider 121. In other embodiments, a third party may own and/oroperate at least a portion of access network 130.

In IP-compliant embodiments of access network 130, access network 130may include a physical layer of unshielded twisted pair cables, fiberoptic cables, a wireless cell data network such as WiMax, or acombination thereof. MCDN 100 may include digital connections betweenclients 120 and a node (see also FIG. 4) in access network 130 whilefiber, cable, WiMax or another broadband medium connects serviceprovider resources to the node. In other embodiments, the broadbandcable may extend all the way to clients 120. In certain embodiments,fiber optic cables may be provided from the node in access network 130to each individual client 120. The connections between access network130 and clients 120 may include digital subscriber line (DSL)connections. In particular embodiments, the connections may beDSL-compliant twisted pair or another type of galvanic loop (see alsoFIG. 4).

As depicted in FIG. 1, switching network 140 provides connectivity forservice provider 121, and may be housed in a central office or otherfacility of service provider 121. Switching network 140 may providefirewall and routing functions to demarcate access network 130 from theresources of service provider 121. In embodiments that employDSL-compliant connections, switching network 140 and/or access network130 may include elements of a DSL access multiplexer (DSLAM) thatmultiplexes many subscriber DSLs to backbone network 170 (see also FIG.4).

In FIG. 1, backbone network 170 represents a private network including,as an example, a fiber based network to accommodate high data transferrates. Content acquisition resources 180 as depicted in FIG. 1 encompassthe acquisition of various types of content including broadcast content,other “live” content including national content feeds, and VOD content.

Thus, the content provided by service provider 121 encompassesmultimedia content that is scheduled in advance for viewing by clients120 via access network 130. Such multimedia content, also referred toherein as “scheduled programming,” may be selected using an electronicprogramming guide (EPG), such as EPG 316 described below with respect toFIG. 3. Accordingly, a user of MCDN 100 may be able to browse scheduledprogramming in advance of the broadcast date and time. Some scheduledprograms may be “regularly” scheduled programs, which recur at regularintervals or at the same periodic date and time (i.e., daily, weekly,monthly, etc.). Programs which are broadcast at short notice orinterrupt scheduled programs are referred to herein as “unscheduledprogramming.”

Acquired content is provided to content delivery server 160 via backbonenetwork 170 and switching network 140. Content may be delivered fromcontent delivery server 160 to clients 120 via switching network 140 andaccess network 130. Content may be compressed, encrypted, modulated,demodulated, and otherwise encoded or processed at content acquisitionresources 180, content delivery server 160, or both. Although FIG. 1depicts a single element encompassing acquisition of all content,different types of content may be acquired via different types ofacquisition resources. Similarly, although FIG. 1 depicts a singlecontent delivery server 160, different types of content may be deliveredby different servers. Moreover, embodiments of MCDN 100 may includecontent acquisition resources in regional offices that are connected toswitching network 140.

Although service provider 121 is depicted in FIG. 1 as having switchingnetwork 140 to which content acquisition resources 180, content deliveryserver 160, and application server 150 are connected, other embodimentsmay employ different switching networks for each of these functionalcomponents and may include additional functional components (notdepicted in FIG. 1) including, for example, operation support systems(OSS) resources.

FIG. 1 also illustrates application server 150 connected to switchingnetwork 140. As suggested by its name, application server 150 may hostor otherwise implement one or more applications for MCDN 100.Application server 150 may, for example, host all or portions of anintercom application 724 (depicted in FIG. 7), which may be downloadedto an intercom unit or other client premises unit. Application server150 may be any data processing system with associated software thatprovides applications for clients or users. Application server 150 mayprovide services including multimedia content services, e.g., EPGs,digital video recording (DVR) services, VOD programs, PPV programs, IPTVportals, digital rights management (DRM) servers, navigation/middlewareservers, conditional access systems (CAS), and remote diagnostics, asexamples.

Applications provided by application server 150 may be downloaded andhosted on other network resources including, for example, contentdelivery server 160, switching network 140, and/or on clients 120.Application server 150 is configured with a processor and storage media(not shown in FIG. 1) and is enabled to execute processor instructions,such as those included within a software application. As depicted inFIG. 1, application server 150 may be configured to include variousapplications (not shown in FIG. 1) that may provide functionality toclients 120.

Further depicted in FIG. 1 is database server 190, which provideshardware and software resources for data storage. Database server 190may communicate with other elements of the resources of service provider121, such as application server 150 or content delivery server 160, inorder to store and provide access to large volumes of data, information,or multimedia content. In some embodiments, database server 190 includesa data storage application, accessible via switching network 140, thatcan be used to record and access structured data, such as program orchannel metadata for clients 120. Database server 190 may also storedevice information, such as identifiers for client 120, modelidentifiers for remote control devices, identifiers for peripheraldevices, etc.

Also shown in FIG. 1 is wireless network 174, which may be coupled toswitching network 140. Wireless network 174 may represent a wirelesscommunications network for providing wireless service to a plurality ofwireless user devices (not shown in FIG. 1). Wireless network 174 mayaccordingly represent an external network that is configured to operateautonomously to MCDN 100, but which may be coupled to MCDN 100. Incertain embodiments, service provider 121 may own and/or operate bothMCDN 100 and wireless network 174. It is further noted that access towireless network 174 may be provided at client 120 via access network130, as will be described in additional detail herein.

In FIG. 1, Internet 172 is representative of any public networkaccessible via switching network 140. Access to Internet 172 mayencompass publication of websites, web pages, and web applications thatmay be invoked using a universal resource locator (URL), such as anInternet web address. A web browser or similar application may be usedto access a published website using an Internet user device (not shownin FIG. 1). In certain implementations, application server 150 and/ordatabase server 190 may be configured to host web servers (not shown inFIG. 1) accessible via Internet 172, whereby the web servers providefunctionality for publishing websites and managing various URLs relatedthereto. It is noted that websites published using MCDN 100 may providecontrolled access based on an MCDN client account associated withindividual client 120. Client-specific websites may thus enableclient-specific information and/or communication channels to be madeavailable by MCDN 100 via Internet 172.

Turning now to FIG. 2, clients 120 are shown in additional detail withrespect to access network 130. Clients 120 may include networkappliances collectively referred to herein as customer premisesequipment (CPE) 122. In the depicted embodiment, CPE 122 includes thefollowing devices: gateway (GW) 123, MHD 125, and display device 126.Any combination of GW 123, MHD 125, and display device 126 may beintegrated into a single physical device. Thus, for example, CPE 122might include a single physical device that integrates GW 123, MHD 125,and display device 126. As another example, MHD 125 may be integratedinto display device 126, while GW 123 is housed within a physicallyseparate device. In some embodiments, CPE 122 may also include anintercom unit such as the intercom unit 322 depicted in FIG. 3 and MHD125 may include an intercom server module 324 and visitor profiles 326depicted in FIG. 3.

In FIG. 2, GW 123 provides connectivity for client 120 to access network130. GW 123 provides an interface and conversion function between accessnetwork 130 and client-side local area network (LAN) 124. GW 123 mayinclude elements of a conventional DSL or cable modem. GW 123, in someembodiments, may further include routing functionality for routingmultimedia content, conventional data content, or a combination of bothin compliance with IP or another network layer protocol. In someembodiments, LAN 124 may encompass or represent an IEEE 802.3 (Ethernet)LAN, an IEEE 802.11-type (WiFi) LAN, or a combination thereof. GW 123may still further include WiFi or another type of wireless access pointto extend LAN 124 to wireless-capable devices in proximity to GW 123. GW123 may also provide a firewall (not depicted) between clients 120 andaccess network 130.

Clients 120 as depicted in FIG. 2 further include a display device or,more simply, a display 126. Display 126 may be implemented as a TV, aliquid crystal display screen, a computer monitor, or the like. Display126 may comply with a display standard for computer monitors and/ortelevision displays. Standards for computer monitors include analogstandards such as video graphics array (VGA), extended graphics array(XGA), etc., or digital standards such as digital visual interface (DVI)and high definition multimedia interface (HDMI), among others. Atelevision display may comply with standards such as National TelevisionSystem Committee (NTSC), Phase Alternating Line (PAL), or anothersuitable standard. Display 126 may include one or more integratedspeakers to play audio content.

Clients 120 are further shown with their respective remote control 128,which is configured to control the operation of MHD 125 by means of auser interface (not shown in FIG. 2) displayed on display 126. Remotecontrol 128 of client 120 is operable to communicate requests orcommands wirelessly to MHD 125 using infrared (IR) or radio frequency(RF) signals. MHDs 125 may also receive requests or commands via buttons(not depicted) located on side panels of MHDs 125.

In some embodiments, remote control 128 may represent a device that isconfigured to control multiple pieces of equipment. When the equipmentcontrolled by remote control 128 changes, remote control 128 may bereprogrammed, for example, to add a new device. Remote control 128 maybe programmed using a local transceiver (see FIG. 3) coupled to CPE 122.

MHD 125 is enabled and configured to process incoming multimedia signalsto produce audio and visual signals suitable for delivery to display 126and any optional external speakers (not depicted in FIG. 2). Incomingmultimedia signals received by MHD 125 may be compressed and/orencrypted, digital or analog, packetized for delivery overpacket-switched embodiments of access network 130 or modulated fordelivery over cable-based access networks. In some embodiments, MHD 125may be implemented as a stand-alone set top box suitable for use in aco-axial or IP-based MCDN. As suggested above, CPE 122 and MHD 125 mayimplement interactive monitoring functionality as discussed in greaterdetail below.

Referring now to FIG. 3, a block diagram illustrating selected elementsof an embodiment of MHD 125 is presented. In FIG. 3, MHD 125 is shown asa functional component of CPE 122 along with GW 123 and display 126,independent of any physical implementation, as discussed above withrespect to FIG. 2. In particular, it is noted that CPE 122 may be anycombination of GW 123, MHD 125 and display 126.

In the embodiment depicted in FIG. 3, MHD 125 includes processor 301coupled via shared bus 302 to storage media, collectively identified asmemory media 310. MHD 125, as depicted in FIG. 3, further includesnetwork adapter 320 that interfaces MHD 125 to LAN 124 and through whichMHD 125 receives multimedia content 360. GW 123 is shown providing abridge between access network 130 and LAN 124, and receiving multimediacontent 360 from access network 130.

In embodiments suitable for use in IP-based content delivery networks,MHD 125, as depicted in FIG. 3, may include transport unit 330 thatassembles the payloads from a sequence or set of network packets into astream of multimedia content. In coaxial-based access networks, contentmay be delivered as a stream that is not packet-based and it may not benecessary in these embodiments to include transport unit 330. In aco-axial implementation, however, CPE 122 may require tuning resources(not explicitly depicted in FIG. 3) to “filter” desired content fromother content that is delivered over the coaxial medium simultaneouslyand these tuners may be provided in MHDs 125. The stream of multimediacontent received by transport unit 330 may include audio information andvideo information, and transport unit 330 may parse or segregate the twoto generate video stream 332 and audio stream 334 as shown.

Video and audio streams 332 and 334, as output from transport unit 330,may include audio or video information that is compressed, encrypted, orboth. A decoder unit 340 is shown as receiving video and audio streams332 and 334 and generating native format video and audio streams 342 and344. Decoder 340 may employ any of various widely distributed videodecoding algorithms including any of the Motion Pictures Expert Group(MPEG) standards, or Windows Media Video (WMV) standards including WMV9, which has been standardized as Video Codec-1 (VC-1) by the Society ofMotion Picture and Television Engineers. Similarly, decoder 340 mayemploy any of various audio decoding algorithms including Dolby®Digital, Digital Theatre System (DTS) Coherent Acoustics, and WindowsMedia Audio (WMA).

The native format video and audio streams 342 and 344 as shown in FIG. 3may be processed by encoders/digital-to-analog converters(encoders/DACs) 350 and 370 respectively to produce analog video andaudio signals 352 and 354 in a format compliant with display 126, whichitself may not be a part of MHD 125.

Memory media 310 encompasses persistent and volatile media, fixed andremovable media, and magnetic and semiconductor media. Memory media 310is operable to store instructions, data, or both. Memory media 310 asshown may include sets or sequences of instructions and/or data, namely,an operating system 312, EPG 316, visitor profiles 326, and intercomserver module 324. Operating system 312 may be a UNIX or UNIX-likeoperating system, a Windows® family operating system, or anothersuitable operating system. In some embodiments, memory media 310 isconfigured to store and execute instructions provided as services toclient 120 by application server 150, as mentioned previously.

EPG 316 represents a guide to the multimedia content provided to MHD 125via MCDN 100, and may be shown to the user as an element of the userinterface. The user interface may include a plurality of menu itemsarranged according to one or more menu layouts, which enable a user tooperate MHD 125. The user may operate the user interface, including EPG316, using remote control 128 (see FIG. 2).

Visitor profiles 326 represent a collection of information aboutspecific visitors to the premises of client 120. Visitor profiles 326may be indexed using an identifier and/or an identity for eachrespective visitor. Visitor profiles 326 may include additionalinformation, such as images, audio recordings, video recordings andother content associated with individual visitors. In addition, visitorprofiles 326 may include configuration information usable for respondingand/or interacting with respective visitors. In certain embodiments, auser of MHD 125 may provide the configuration information to configureMHD 125 and/or intercom unit 322 to respond with desired actions orfunctionality when a visitor is detected within a proximity of thepremises of client 120. For example, MHD 125, in conjunction withintercom unite 322, may attempt to identify the visitor and/or initiatecommunication with or provide information to the visitor. It is notedthat in certain embodiments, visitor profiles 326 may be configured tostore configuration information using MCDN 100, for example, inconjunction with database server 190 (see FIG. 1).

Intercom server module 324 may represent an application for managingfunctionality and communication with a number of intercom units, such asintercom unit 322. In particular embodiments, intercom server module 324may communicate via intercom link 328 with intercom client 734 (see FIG.7) executing on intercom unit 322. Intercom server module 324 may alsoinclude interactive functionality, such as a user interface, foroperation by a user of MHD 125. In some embodiments, intercom servermodule 324 may be configured to access visitor profiles 326 to save orretrieve user-specific and/or visitor-specific information in order toprovide desired intercom functionality, as will be described inadditional detail herein.

Local transceiver 308 represents an interface of MHD 125 forcommunicating with external devices, such as remote control 128, oranother remote control device. Local transceiver 308 may provide amechanical interface for coupling to an external device, such as a plug,socket, or other proximal adapter. In some cases, local transceiver 308is a wireless transceiver, configured to send and receive infrared (IR)or radio frequency (RF) or other signals. In some implementations localtransceiver 308 receives IR or RF signals, but does not transmit IR orRF signals, i.e., local transceiver 308 may be a receiver. Localtransceiver 308 may be accessed by a remote control module (not shown inFIG. 3) for providing remote control functionality. In some embodiments,local transceiver 308 may include WiFi functionality.

Wireless telemetry interface 318 represents a wireless transceiver thatmay be configured to provide MHD 125 with voice and/or datacommunications. In particular embodiments, wireless telemetry interface318 may be serviced by wireless network 174 (see FIGS. 1 and 4), suchthat MHD 125 is a wireless device of wireless network 174. It is notedthat in certain embodiments wireless telemetry interface 318 may beimplemented using an electronic device or component integrated withinMHD 125. In other instances, wireless telemetry interface 318 may be anexternal device (not shown in FIG. 3), such as a cellular telephone orwireless communication device, that may be coupled to MHD 125 to provideconnectivity with wireless network 174. Wireless telemetry interface 318may further be configured for machine to machine (M2M) capability withcorresponding systems and communication devices for a variety ofapplications. For example, M2M may be used by wireless telemetryinterface 318 to monitor status information about the premises of client120 and transmit the status information to a provider of home monitoringservices, which may be the service provider 121 depicted in FIG. 1 or athird party service provider. MHD 125 may further rely upon the M2Mcapability of wireless telemetry interface 318 as an MCDN backupcommunication channel, for example, when GW 123 and/or access network130 are unavailable. In some instances, wireless telemetry interface 318may be enabled for push-to-talk (PTT) and/or push-to-talk over cellular(POC), in which wireless telemetry interface 318 switches between avoice reception mode and a transmit mode, e.g., by pushing or releasinga PTT button or other control (not depicted), thereby providing moreimmediate communication with a shorter connection time than, forexample, a conventional cellular telephone connection.

Intercom unit 322 (see also FIG. 7), is depicted coupled to MHD 125 viaintercom link 328. Intercom unit 322 may provide intercom functionalityat the premises of client 120, including monitoring and reception ofvisitors, in conjunction with MHD 125, as will be described in furtherdetail below. In various embodiments, intercom link 328 may represent alocal communication link established using local transceiver 308,network adapter 320, shared bus 302, wireless telemetry interface 318,or another suitable interface (not shown in FIG. 3). In other words,intercom link 328 may represent a dedicated physical or logical networksegment for communicating between MHD 125 and intercom unit 322 (seealso FIG. 4). It is noted that intercom link 328 may represent awireless or fixed communication link (including optical or galvanicconnectors) or a combination thereof.

Turning now to FIG. 4, a block diagram of selected elements of anembodiment of home monitoring system 400 is depicted. It is noted thatelements in FIG. 4 represent like-numbered elements discussed above withrespect to FIGS. 1-3. Home monitoring system 400 may employ an exemplaryarchitecture for interactive home monitoring in conjunction with anMCDN, as described herein. In various embodiments, certain elements inhome monitoring system 400 may be omitted or rearranged to performinteractive home monitoring.

In FIG. 4, home monitoring system 400 is shown including home monitoringequipment 402, which may encompass certain elements of CPE 122 (see alsoFIG. 3). As shown in FIG. 4, MHD 125, display 126, GW 123 and LAN 124may represent elements of CPE 122 that are configured for use with MCDN100 (see FIGS. 1-3). Home monitoring equipment 402 may represent one ormore components installed at the premises of client 120 for interactivehome monitoring, as will be described in further detail below.

As shown in FIG. 4, home monitoring equipment 402 is shown includingintercom link 328, which may provide connectivity among a number ofintercom units 322 and MHD 125. Intercom link 328 may service one ormore intercom units 322, such as intercom unit 322-1, intercom unit322-2, and so on up to intercom unit 322-p, where p is an integer numberof installed intercom units 322. In some embodiments, intercom units 322may be installed at entry points or entrances of the premises of client120. Intercom units 322 may be configured to communicate via MHD 125 orto communicate in a peer-to-peer fashion among themselves.

In the depicted embodiment of home monitoring system 400, MHD 125 may beconfigured to use LAN 124 as well as wireless link 414, which representsa wireless connection between wireless telemetry interface 318 (see FIG.3) and wireless network 174. Via LAN 124 and/or GW 123, MHD 125 may bein communication with home security monitor 406, which may represent adedicated controller for home security applications. Specifically, homesecurity monitor 406 may be configured to control x number of actuators408 and monitor m number of sensors 404, where x and m are integers. Itis noted that home security monitor 406 may be configured to communicatewith intercom server module 324 (see FIG. 3) executing on MHD 125 toreceive commands and/or to provide status information describing sensors404 and actuators 408. It is noted that home security monitor 406 andits associated sensors 404 and actuators 408 may represent a stand-alonesystem that is provided by an external service provider (not shown inthe drawings). It is further noted that, in given embodiments, homesecurity monitor 406 may represent various alternative architectures,such as a distributed architecture with multiple controllers, asegmented architecture covering different locations, or a redundantarchitecture with backup monitoring and control elements.

Actuators 408 may represent servo or mechanical actuators forcontrolling equipment at the premises of client 120. For example,actuator 408-1 may control (i.e., actuate) a door lock or a door lockrelease mechanism in response to a control signal (i.e., controlcommand) generated by home security monitor 406. Similarly, actuator408-1 may control a window opening or locking mechanism. Various othertypes of actuators 408 may be implemented. It is noted that homesecurity monitor 406 may also be configured to receive or monitor astatus for an actuator 408, which may enable home security monitor 406to confirm that a desired or expected state of an actuator 408 hasactually been attained after a control command has been sent. In certaininstances, an actuator 408 itself includes an embedded controllercapable of communicating with home security monitor 406.

In addition, home security monitor 406 may be configured to monitorsensors 404, which are installed at the premises of client 120. Sensors404, may represent various types of transducers or measuring sensors.For example, sensor 404-1 may represent a window position sensor, whilesensor 404-2 may represent a door closing sensor. Various types andconfigurations of sensors 404 may be used with home security monitor406. In certain instances, a sensor 404 may be a so-called ‘smartsensor’ with internal data processing and communications capability.

Also in FIG. 4, access network 130, switching network 140, wirelessnetwork 174, and Internet 172 may represent elements of MCDN 100, asdiscussed previously (see also FIG. 1). Wireless network 174 may providewireless service 416 to wireless user device 410, which may represent amobile telephony device, such as a cellular telephone, smart phone, orother types of devices, such as media players, music players, or networkaccess devices. Wireless user device 410 may also be a portable computeror a personal computer configured with wireless capability. Similarly,Internet user device 412 may represent a networked computing deviceoperated by a user, for example, using a web browser. Accordingly,Internet user device 412 may be a personal computer, a portablecomputer, or another of various types of networked computing devices.

In operation of home monitoring system 400, a user of client 120 mayoperate MHD 125, wireless user device 410, and/or Internet user device412, to configure intercom server module 324 for functionality tocommunicate with intercom unit 322. For example, a user may populatevisitor profiles 326 with information about specific individuals andwhich actions to take when such individuals are detected as visitors tothe premises of client 120. After configuration, home monitoringequipment 402 may detect a visitor in proximity of the premises ofclient 120. Specifically, a visitor may be detected approaching intercomunit 322-1, which may be used to interact with the visitor. In certaininstances, an image of an arriving visitor may be compared with an imagestored in visitor profiles 326. When a match is detected, homemonitoring equipment 402 may set a visitor status to ‘known’ and mayproceed to perform predetermined tasks. When no match is detected, homemonitoring equipment 402 may set the visitor status to ‘unknown’ andstore an image of the visitor for future reference, for example, invisitor profiles 326.

Intercom unit 322-1 may also perform various tasks to interact with avisitor. When the visitor status is known, intercom unit 322-1 maydisplay or output a message intended for the visitor. The message mayinclude a predetermined greeting or visitor-specific information.Depending on the visitor status, the visitor may be allowed to operateintercom unit 322-1 to obtain additional information or to leave apersonalized message for the user. In certain embodiments, intercom unit322-1 may establish a direct communication channel with the user, viawireless telemetry interface 318. The communication channel may befull-duplex or half-duplex in providing bidirectional communication. Theuser may thus be enabled to communicate using wireless user device 410or Internet user device 412. It is noted that the user may be located ata remote location from the premises of client 120. When desired, theuser may be provided with a real-time communication channel to intercomunit 322-1. For example, a PTT channel may be established via wirelessnetwork 174 between intercom unit 322-1 and wireless user device 410.The visitor may or may not be made aware of the user's location, forexample, depending on the visitor status. The user may further beenabled to control home monitoring equipment 402 remotely while thevisitor is interacting with intercom unit 322-1. For example, the usermay sample an output of any of the sensors 404 or allow the visitor toenter the premises of client 120, by sending a command to home securitymonitor 406 to control a corresponding actuator 408. In certaininstances, the visitor may not be made aware that the user is monitoringthe visitor's presence and/or activity. The visitor's identity andactivity may be recorded by MHD 125 and the user may be enabled toreview information recorded for all visitors over a given time period.In this manner, for example, the user may review visitor messages and/orvisitor reports for the previous day, week or other period. It is notedthat intercom server module 324 and/or application server 150 (seeFIG. 1) may provide a user application for interactive home monitoring,as described herein, that is executable on wireless user device 410and/or Internet user device 412.

In operation of home monitoring system 400, home monitoring equipment402 may be configured to provide certain security features at thepremises of client 120. For example, since MHD 125 may communicate withhome security monitor 406, the user may be notified when a securitybreach is detected by home security monitor 406 via wireless network174. In certain embodiments, MHD 125 may be configured to detect whenaccess network 130 is unavailable and to use communication link 414 as abackup to communicate with MCDN 100 via switching network 140. In thismanner, interactive home monitoring, along with other MCDNfunctionality, may remain operational during a situation when, forexample, a connection to access network 130 has been innocently ormaliciously interrupted. When sensor 404 and/or intercom unit 322includes an imaging device, home monitoring equipment 402 may beconfigured to provide real-time images of the premises of client 120 towireless user device 410. In this manner, remote surveillancefunctionality may be provided to the user, regardless of location.

In addition, home monitoring equipment 402 may record visitor activityand interaction with intercom units 322 and generate visitor reports forthe MCDN user. The MCDN user may request a visitor report, for exampleusing intercom server module 324, for a specified period of time, suchas the previous day, week, month, etc. The visitor report for thespecified period of time may be generated and may include identificationinformation for visitors, along with indications of arrival times ofrespective visitors. The visitor report may also include, or provideaccess to, captured images of the visitors that have been stored. Inthis manner, the MCDN user may review all visitor activity recorded byhome monitoring equipment 402.

It is further noted that additional functionality using home monitoringequipment 402 may be provided by executable code included in intercomserver module 324. For example, intercom server module 324 may beconfigured to use wireless network 174 for a variety of functions, suchas, but not limited to, notifying the MCDN user that the visitor wasdetected, sending an image of the visitor to the MCDN user, sending avisitor status to the MCDN user, communicating bidirectionally betweenthe visitor and the MCDN user, communicating via audio, communicatingvia video, communicating via text, receiving instructions from the MCDNuser for interfacing with the visitor, or combinations thereof. FIG. 4thus depicts an implementation of home monitoring equipment forinteractively monitoring a client premises in which MHD 125 may use awireless telemetry interface as a backup network interface when accessnetwork 130 or other aspects of MCDN 100 are unavailable

Turning now to FIG. 5, selected elements of an embodiment of a method500 for interactive home monitoring are illustrated in flow chart form.In one embodiment, method 500 may be performed by intercom server module324 (see FIG. 3) in conjunction with MCDN 100 and home monitoring system400 (see FIGS. 1, 4). Method 500 may also involve functionality providedby intercom application 734 executing on intercom unit 322 (see FIGS. 3,4, and 7). It is noted that certain operations described in method 500may be optional or may be rearranged in different embodiments.

In method 500, an arrival indication indicating that a visitor is inproximity of an MCDN client premises may be received (operation 502),e.g., by MHD 125 from intercom unit 322. The arrival indication may beautomatically generated without direct visitor input. In someembodiments, the arrival indication may be generated responsive tovisitor input at the intercom unit. Based on a captured image orcaptured audio data of the visitor, an identity of the visitor may bedetermined (operation 504). The image may be captured by the intercomunit. The identity of the visitor may be determined using a biometricanalysis of at least a portion of the image, such as a portion includinga facial image of the visitor. Status information may be received(operation 506) from a home security monitor. The status information mayindicate whether the MCDN client premises are in a secured or desiredcondition. A determination may then be made (operation 508) whether theidentity is a known identity. The determination may be made by comparingknown (i.e., previously stored) identity information with the identityof the visitor.

When the visitor identity is a known identity, then a visitor profilemay be queried (operation 510) based on the identity. In someembodiments, operation 510 may be combined with operation 504. In thisbranch of method 500, it may be assumed that identity information, suchas a visitor profile, has previously been stored for the visitor. Assuch, a communication channel may be established (operation 512) with anMCDN user via a wireless interface. The MCDN user may be a registereduser of the MCDN client. The wireless interface may be configured toestablish the communication channel with a wireless user deviceassociated with the MCDN user, for example, using M2M capability. Incertain embodiments, the communication channel may be a PTT channel. TheMCDN user and the visitor may use the communication channel tocommunicate with each other via voice, image, video or a combinationthereof. For example, the MCDN user may be shown an image of the visitorwhile engaging in a PTT interchange of voice messages with the visitor.The visitor may be shown an image of the MCDN user. Next, informationmay be provided (operation 514) to the visitor according to the visitorprofile. The information may be provided in response to requests orselections made by the visitor using the intercom unit. The visitorprofile may be used to determine the type of information or the type ofaccess provided to the visitor. That is, the visitor profile may includeconfiguration information provided by the MCDN user and specific to thevisitor that constrains the functionality provided by the intercom unitto the visitor.

When the visitor identity is not known, then a new visitor profile maybe created (operation 520). In this branch of method 500, it may beassumed that the visitor is a new visitor and that no visitor profileexists for the new visitor. The captured image may be identified, e.g.,“Unknown visitor 0001”, and added (operation 522) to the visitorprofile. The captured image may be made available for comparing withcaptured images of future visitors that come into proximity of the MCDNclient premises. Thus, FIG. 5 depicts a method for providing interactivemonitoring at a client premises, where the method may includeestablishing, with a wireless interface of the MHD, a wirelessbidirectional audio communication channel between the MHD and a mobileuser device associated with an MCDN user of the client premises.

Turning now to FIG. 6, selected elements of an embodiment of method 600for interactive home monitoring are illustrated in flow chart form. Inone embodiment, method 600 may be performed by intercom server module324 (see FIG. 3) in conjunction with MCDN 100 and home monitoring system400 (see FIGS. 1, 4). Method 600 may also involve functionality providedby intercom application 734 executing on intercom unit 322 (see FIGS. 3,4, and 7). It is noted that certain operations described in method 600may be optional or may be rearranged in different embodiments.

In the depicted embodiment, method 600 detects (operation 602) a visitorbased on an image acquired at an intercom unit locally coupled to anMCDN client. The image may be acquired by the intercom unit in responseto the visitor coming in proximity of the MCDN client premises. Theimage may be sent to CPE 122 associated with MCDN client 120 viaintercom link 328 (see FIGS. 3 and 4). The image may be compared(operation 604) to stored images and/or stored visitor profiles for amatch. A determination may be made (operation 606) whether a match isdetected.

If a match is detected, then the visitor may be identified and a visitorstatus may be set to ‘known’ (operation 608). A communication channelmay be established (operation 610) with an MCDN user. The communicationchannel may include a wireless connection to the MCDN user, who may belocated remotely from the MCDN client premises. The communicationchannel may be established to a network address associated with the MCDNuser. In certain embodiments, the network address is a cellulartelephone number registered to the MCDN user. The network address mayalso include an IP address, for example, for Internet user device 412(see FIG. 4). Establishing the communication channel in operation 608may further be dependent on configuration information associated with avisitor profile for the identified visitor.

In one embodiment, for certain visitors having a known visitor status,operation 610 may be omitted according to predetermined preferencesprovided by the MCDN user.

If no match is detected in operation 606, then a visitor status may beset (operation 620) to ‘unknown’. It is noted that certain additionaloperations (not shown in FIG. 6) may be implemented during interactivehome monitoring for visitors having an unknown visitor status. Forexample, recordings of visitor actions or behavior may be stored whenthe visitor status is unknown. Next, a new visitor profile including theacquired image may be created (operation 622). The visitor profile mayinclude an unknown or new visitor identity, which the MCDN user maysubsequently access and modify or supplement. It is noted that incertain embodiments, the MCDN user may be notified in real-time of thepresence of the unknown visitor (not shown in FIG. 6).

Irrespective of the outcome of operation 606, information may beprovided (operation 612) to the visitor based on the visitor status.Different information or accessibility may be provided to the visitor atthe intercom unit depending on the visitor status. For example, knownvisitors may be provided with prerecorded messages or communicationsfrom the MCDN user specifically intended for the visitor. In certaininstances, an unknown visitor may be given an opportunity to identifythemselves at the intercom unit, which may cause portions of method 600to loop or repeat (not shown in FIG. 6). Method 600 may further enable(operation 618) the MCDN user may be enabled to monitor sensors and tocontrol actuators. The sensors and actuators may be accessed via a homesecurity monitor located at the MCDN client premises and coupled to CPEof the MCDN. Method 600 as depicted in FIG. 6 thus emphasizes theproviding of information to the visitor and the enabling of the MCDNuser to monitor sensors and control actuators whereas the method 500depicted in FIG. 5 emphasizes the establishing of a communicationchannel with the MCDN user via a wireless interface.

Referring now to FIG. 7, a block diagram illustrating selected elementsof an embodiment of intercom unit 322 is presented. Intercom unit 322may represent an embedded device that is installed at an entry point tothe premises of MCDN client 120. As shown in FIG. 4, multiple instancesof intercom unit 322 may be configured for use at a given MCDN clientpremises. Intercom unit 322 may be installed in a manner that isamenable for viewing and/or operation by visitors to the MCDN clientpremises and may be coupled to MHD 125 via intercom link 328. In certainimplementations, intercom unit 322 may be located at a considerabledistance from MHD 125, for example, at an entry gate that is severalhundred meters (or further) away from where CPE 122 is installed. Theelements of intercom unit 322 depicted in FIG. 7 may be physicallyimplemented as a single, self-contained device. In certainimplementations, intercom unit 322 may alternatively be implementedusing a number of different devices that are physically separated, butcoupled together for centralized control. It is noted that intercom unit322 may include additional components, such as a power supply and acooling element, which have been omitted from FIG. 7 for clarity. Asshown in FIG. 7, intercom unit 322 may operate in conjunction with MHD125 (see also FIGS. 3 and 4) to execute the methods and operationsdescribed herein.

In the embodiment depicted in FIG. 7, intercom unit 322 includes aprocessor 702 coupled via shared bus 701 to storage media collectivelyidentified as memory media 730. Intercom unit 322, as depicted in FIG.7, further includes communication interface 704 that interfaces intercomunit 322 to MHD 125 via interface link 328, and through which intercomunit 322 may communicate with other elements of MCDN 100 (see FIG. 1) aswell as with user devices, such as wireless user device 410 and Internetuser device 412 (see FIG. 4). Also shown coupled to shared bus 701 aredisplay 706, audio output 708, audio input 710, control elements 714,and imaging sensor 712. As described herein, intercom unit 322 may beconfigured to output multimedia content, including audio content, videocontent, images, text, or combinations thereof.

Display 706 may be implemented as a TV, a liquid crystal display screen,a computer monitor, or the like. Display 706 may comply with a displaystandard for computer monitors and/or television displays. Standards forcomputer monitors include analog standards such as VGA, XGA, etc., ordigital standards such as DVI, HDMI, among others. A television displaymay comply with standards such as NTSC, PAL, or another suitablestandard.

Audio output 708 may represent one or more speakers to play audiocontent and may, in certain instances, represent a set of speakerslocated at various locations. In this manner, audio output 708 may beconfigured to attain certain audio effects or a desired audio quality.Similarly, audio input 710 may represent a microphone or audiotransducer for capturing audio input, including speech, provided byvisitors and other users of intercom unit 322. Control elements 714 mayrepresent physical or virtual controls, such as buttons, knobs, sliders,etc., that may be operated by visitors and other users of intercom unit322. In particular embodiments, control elements 714 include virtualcontrol elements displayed by display 706 and operable using a touchsensor, such as a touch screen or other tactile sensor. Accordingly,control elements 714 may represent static as well as dynamic controlsthat may be reconfigured for various input and output functions, asdesired. Imaging sensor 712 may represent a camera for obtaining stilland video imagery within a proximity of intercom unit 322. In variousembodiments, intercom application 734 may be configured to acquire andprocess image data obtained using imaging sensor 712.

Memory media 730 encompasses persistent and volatile storage media,fixed and removable storage media, and magnetic and semiconductorstorage media. Memory media 730 is operable to store instructions, data,or both. Memory media 730 as shown may include sets or sequences ofinstructions, including an operating system 732, and intercomapplication 734. Operating system 706 may be a UNIX or UNIX-likeoperating system, a Windows® family operating system, or anothersuitable operating system. Intercom application 734 may be configured toexchange instructions and data with intercom server module 324 (see FIG.3) and to provide an interface for use by visitors to the MCDN clientpremises. Specifically, intercom application 734 may be configured toacquire images of visitors, output audio messages to visitors, receiveaudio messages from visitors, provide a graphical interface for displayto visitors, receive commands and selections from visitors, and performvisitor-specific operations in conjunction with other elements in homemonitoring equipment 402 (see FIG. 4). It is noted that intercomapplication 734 may execute certain methods and operations describedherein, such as portions of method 500 (see FIG. 5) and/or method 600(see FIG. 6), or other operations.

To the maximum extent allowed by law, the scope of the presentdisclosure is to be determined by the broadest permissibleinterpretation of the following claims and their equivalents, and shallnot be restricted or limited to the specific embodiments described inthe foregoing detailed description.

What is claimed is:
 1. A home monitoring method, comprising: receivingencoded multimedia content corresponding to scheduled programming froman access network via a network adapter; decoding the multimedia contentreceived from the access network to generate a decoded audio signal anda decoded video signal; receiving an image and audio of a visitor froman intercom unit via a wireless telemetry interface; determining, basedon the image received and a collection of stored visitor profiles, avisitor status selected from: known or unknown; generating, based on thevisitor status, a visitor prompt, wherein the visitor prompt indicatesan identity of the visitor when the visitor status is known; responsiveto determining that the visitor status is known, retrieving a visitorprofile for the visitor; responsive to determining that the visitorstatus is unknown, adding, to the collection, a new visitor profileincluding the image and audio received and the visitor status;generating, based on the visitor profile, a visitor prompt appropriatefor the visitor status, wherein the visitor prompt indicates an identityof the visitor when the visitor status is known; and establishing acommunication connection between a network user and the visitor via thewireless telemetry interface.
 2. The method of claim 1, furthercomprising: detecting a request from the visitor for premisesinformation; and responsive to the request, outputting premisesinformation via the intercom unit, based on the visitor status.
 3. Themethod of claim 1, wherein the intercom unit is configured to outputmultimedia content, including at least one of: audio content, videocontent, images, and text.
 4. The method of claim 1, whereinestablishing the communication connection includes a cellular telephoneconnection.
 5. The method of claim 1, wherein establishing thecommunication connection includes an Internet protocol connection. 6.The method of claim 1, further comprising: using the communicationconnection to perform at least one of: notifying the network user thatthe visitor was detected; sending the image to the network user; sendingthe visitor status to the network user; communicating bidirectionallybetween the visitor and the network user; communicating via audio;communicating via video; communicating via text; and receivinginstructions from the network user for interfacing with the visitor. 7.A premises device, comprising: a processor; a network adapter; awireless telemetry interface; and a computer readable memory, accessibleto the processor, including processor executable instructions, which,when executed by the processor, cause the processor to performoperations comprising: receiving encoded multimedia contentcorresponding to scheduled programming from an access network via anetwork adapter; and decoding the multimedia content received from theaccess network to generate a decoded audio signal and a decoded videosignal; detecting a visitor in proximity to a premises of a client basedon an image and audio of the visitor received from an intercom unit viathe wireless telemetry interface; receiving, from the intercom unit, anarrival indication initiated by the visitor; determining an identity ofthe visitor based on the image; and responsive to determining that thevisitor status is known, retrieving a visitor profile for the visitor;responsive to determining that the visitor status is unknown, adding, tothe collection, a new visitor profile including the image and audioreceived and the visitor status; generating, based on the visitorprofile, a visitor prompt appropriate for the visitor status, whereinthe visitor prompt indicates an identity of the visitor when the visitorstatus is known; establishing a communication connection between anetwork user and the visitor via the wireless telemetry interface. 8.The device of claim 7, wherein the wireless telemetry interface includesa cellular telephony interface and further wherein the cellulartelephony interface is provided by a cellular telephone device coupledto the processor.
 9. The device of claim 7, wherein the operationsinclude: receiving the encoded multimedia content via the wirelesstelemetry interface responsive to detecting that content is unavailablefrom the access network via the network adapter.
 10. The device of claim7, wherein the intercom link includes at least one of: a wireless link,an optical link, and a wireline link.
 11. The device of claim 7, furthercomprising: a network connection to a home security monitor; wherein theoperations include: receiving, from the home security monitor, sensorinformation from a security sensor installed at the premises; andforwarding the sensor information to the network user.
 12. The device ofclaim 11, wherein the operations include: receiving, from the networkuser, control information to control an actuator installed at thepremises; forwarding the control information to the home securitymonitor; receiving, from the home security monitor, actuator informationindicating a state of the actuator; and forwarding the actuatorinformation to the network user.
 13. A non-transitory computer readablemedium, including processor executable instructions, which when executedby a processor, cause the processor to perform operations including:receiving encoded multimedia content corresponding to scheduledprogramming from an access network via a network adapter; and decodingthe multimedia content received from the access network to generate adecoded audio signal and a decoded video signal; receiving, from anintercom unit, an image and audio of a visitor; determining, based onthe image received and a collection of stored visitor profiles, avisitor status selected from: known or unknown; generating, based on thevisitor status, a visitor prompt, wherein the visitor prompt indicatesan identity of the visitor when the visitor status is known; responsiveto determining that the visitor status is known, retrieving a visitorprofile for the visitor; responsive to determining that the visitorstatus is unknown, adding, to the collection, a new visitor profileincluding the image and audio of the visitor and the visitor status;generating, based on the visitor profile, a visitor prompt appropriatefor the visitor status, wherein the visitor prompt indicates an identityof the visitor when the visitor status is known; establishing acommunication connection between a network user and the visitor via awireless telemetry interface.
 14. The nontransitory computer readablemedium of claim 13, wherein the operations include: detecting a requestfrom the visitor for premises information; and responsive to therequest, outputting premises information via the intercom unit, based onthe visitor status.
 15. The nontransitory computer readable medium ofclaim 13, wherein the intercom unit is configured to output multimediacontent, including at least one of: audio content, video content,images, and text.
 16. The nontransitory computer readable medium ofclaim 13, wherein establishing the communication connection includes acellular telephone connection.
 17. The nontransitory computer readablemedium of claim 13, wherein establishing the communication connectionincludes an Internet protocol connection.
 18. The nontransitory computerreadable medium of claim 13, wherein the operations include: performing,via the communication connection, at least one operation selected from:notifying the network user that the visitor was detected; sending theimage to the network user; sending the visitor status to the networkuser; communicating bidirectionally between the visitor and the networkuser; communicating via audio; communicating via video; communicatingvia text; and receiving instructions from the network user forinterfacing with the visitor.